Skip to content

tidb-cloud: add storage billing explanations#23186

Merged
ti-chi-bot[bot] merged 8 commits into
pingcap:release-8.5from
lilin90:add-storage-explanation
Jul 2, 2026
Merged

tidb-cloud: add storage billing explanations#23186
ti-chi-bot[bot] merged 8 commits into
pingcap:release-8.5from
lilin90:add-storage-explanation

Conversation

@lilin90

@lilin90 lilin90 commented Jul 1, 2026

Copy link
Copy Markdown
Member

What is changed, added or deleted? (Required)

Expand the billing doc with storage model guidance, including standard row-based storage, Infrequent Access row-based storage, and TiFlash-powered columnar storage. The update also adds IA caveats (experimental/region-limited), enablement SQL for TiFlash replicas, and dual-layer encryption details with compliance-focused use cases.

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

  • master (the latest development version)
  • v9.0 (TiDB 9.0 versions)
  • v8.5 (TiDB 8.5 versions)
  • v8.1 (TiDB 8.1 versions)
  • v7.5 (TiDB 7.5 versions)
  • v7.1 (TiDB 7.1 versions)
  • v6.5 (TiDB 6.5 versions)
  • v6.1 (TiDB 6.1 versions)

What is the related PR or file link(s)?

  • This PR is translated from:
  • Other reference link(s):

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

Expand the billing doc with storage model guidance, including standard row-based storage, Infrequent Access row-based storage, and TiFlash-powered columnar storage. The update also adds IA caveats (experimental/region-limited), enablement SQL for TiFlash replicas, and dual-layer encryption details with compliance-focused use cases.
@lilin90 lilin90 self-assigned this Jul 1, 2026
@lilin90 lilin90 added translation/no-need No need to translate this PR. area/tidb-cloud This PR relates to the area of TiDB Cloud. for-cloud-release This PR is related to TiDB Cloud release. labels Jul 1, 2026
@ti-chi-bot ti-chi-bot Bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jul 1, 2026

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds new documentation sections to tidb-cloud-billing.md covering Row-based storage, Row-based storage with Infrequent Access (IA), Columnar storage, and Dual-layer encryption. The review feedback focuses on aligning the text with the style guide by adopting the active voice and second-person perspective, removing repetitive wording, fixing a sentence fragment, and using lowercase for common nouns.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread tidb-cloud/tidb-cloud-billing.md Outdated
Comment thread tidb-cloud/tidb-cloud-billing.md Outdated
Comment thread tidb-cloud/tidb-cloud-billing.md
Comment thread tidb-cloud/tidb-cloud-billing.md Outdated
Comment thread tidb-cloud/tidb-cloud-billing.md
Comment thread tidb-cloud/tidb-cloud-billing.md Outdated
Comment thread tidb-cloud/tidb-cloud-billing.md Outdated
@lilin90 lilin90 requested a review from zhaoshangzi July 1, 2026 10:26
Comment thread tidb-cloud/tidb-cloud-billing.md Outdated

### Row-based storage

Standard row-based storage stores data in **TiKV**. You can set the table's **Storage Class** to `Standard` using the following SQL statement or leave it unset (`NULL`).

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TiDB table is row-based by default, which stores data in TiKV

Comment thread tidb-cloud/tidb-cloud-billing.md Outdated
Comment thread tidb-cloud/tidb-cloud-billing.md Outdated
@ti-chi-bot

ti-chi-bot Bot commented Jul 2, 2026

Copy link
Copy Markdown

@zhaoshangzi: adding LGTM is restricted to approvers and reviewers in OWNERS files.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@lilin90 lilin90 added the lgtm label Jul 2, 2026
@lilin90

lilin90 commented Jul 2, 2026

Copy link
Copy Markdown
Member Author

/approve

@ti-chi-bot

ti-chi-bot Bot commented Jul 2, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lilin90

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot Bot added the approved label Jul 2, 2026
@ti-chi-bot ti-chi-bot Bot merged commit 1779968 into pingcap:release-8.5 Jul 2, 2026
11 checks passed
@lilin90 lilin90 deleted the add-storage-explanation branch July 2, 2026 03:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved area/tidb-cloud This PR relates to the area of TiDB Cloud. for-cloud-release This PR is related to TiDB Cloud release. lgtm size/M Denotes a PR that changes 30-99 lines, ignoring generated files. translation/no-need No need to translate this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants